System and method for detection and deployment of virtualization capable assets in a managed datacenter

ABSTRACT

A datacenter management server includes a datacenter operations manager and a datacenter infrastructure manager with an infrastructure viewer and an asset deployment tool. The datacenter operations manager compiles datacenter hierarchy information for a datacenter, including identity information for a virtualized environment and identity information for a virtualization capable system. The virtualization capable system is deployed as a stand-alone system of the datacenter. The datacenter infrastructure manager receives the datacenter hierarchy information, directs the infrastructure viewer to display a hierarchical overview of the datacenter, including depictions of the virtualized environment and the virtualization capable system. The hierarchical overview is based on the identity information. The datacenter infrastructure manager also receives a selection of the depictions from a user and directs the asset deployment tool to deploy the virtualization capable system to the virtualized environment.

CROSS REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No.13/340,817, entitled “System and Method for Detection and Deployment ofVirtualization Capable Assets in a Managed Datacenter,” filed on Dec.30, 2011, the disclosure of which is hereby expressly incorporated byreference in its entirety.

FIELD OF THE DISCLOSURE

The present disclosure generally relates to information handlingsystems, and more particularly relates to detection and deployment ofvirtualization capable assets in a managed datacenter.

BACKGROUND

As the value and use of information continues to increase, individualsand businesses seek additional ways to process and store information.One option is an information handling system. An information handlingsystem generally processes, compiles, stores, or communicatesinformation or data for business, personal, or other purposes.Technology and information handling needs and requirements can varybetween different applications. Thus information handling systems canalso vary regarding what information is handled, how the information ishandled, how much information is processed, stored, or communicated, andhow quickly and efficiently the information can be processed, stored, orcommunicated. The variations in information handling systems allowinformation handling systems to be general or configured for a specificuser or specific use such as financial transaction processing, airlinereservations, enterprise data storage, or global communications. Inaddition, information handling systems can include a variety of hardwareand software resources that can be configured to process, store, andcommunicate information and can include one or more computer systems,graphics interface systems, data storage systems, and networkingsystems. Information handling systems can also implement variousvirtualized architectures.

BRIEF DESCRIPTION OF THE DRAWINGS

It will be appreciated that for simplicity and clarity of illustration,elements illustrated in the Figures are not necessarily drawn to scale.For example, the dimensions of some elements may be exaggerated relativeto other elements. Embodiments incorporating teachings of the presentdisclosure are shown and described with respect to the drawings herein,in which:

FIG. 1 is a block diagram of a managed datacenter according to anembodiment of the present disclosure;

FIGS. 2 and 3 illustrate a method of detecting and deployingvirtualization capable assets in the managed datacenter of FIG. 1according to an embodiment of the present disclosure;

FIGS. 4 and 5 illustrate a hierarchical overview of the manageddatacenter of FIG. 1 according to an embodiment of the presentdisclosure; and

FIG. 6 is a block diagram illustrating an information handling systemaccording to an embodiment of the present disclosure.

The use of the same reference symbols in different drawings indicatessimilar or identical items.

DETAILED DESCRIPTION OF THE DRAWINGS

The following description in combination with the Figures is provided toassist in understanding the teachings disclosed herein. The descriptionis focused on specific implementations and embodiments of the teachings,and is provided to assist in describing the teachings. This focus shouldnot be interpreted as a limitation on the scope or applicability of theteachings.

FIG. 1 illustrates a managed datacenter 100 that can include one or moreinformation handling systems. For purposes of this disclosure, theinformation handling system may include any instrumentality or aggregateof instrumentalities operable to compute, classify, process, transmit,receive, retrieve, originate, switch, store, display, manifest, detect,record, reproduce, handle, or utilize any form of information,intelligence, or data for business, scientific, control, entertainment,or other purposes. For example, an information handling system may be apersonal computer, a PDA, a consumer electronic device, a network serveror storage device, a switch router or other network communicationdevice, or any other suitable device and may vary in size, shape,performance, functionality, and price. The information handling systemmay include memory, one or more processing resources such as a centralprocessing unit (CPU) or hardware or software control logic, andoperates to execute code. Additional components of the informationhandling system may include one or more storage devices that can storecode, one or more communications ports for communicating with externaldevices as well as various input and output (I/O) devices, such as akeyboard, a mouse, and a video display. The information handling systemmay also include one or more buses operable to transmit communicationsbetween the various hardware components.

In a particular embodiment, managed datacenter 100 includes a virtualmachine environment 110, one or more additional virtual machineenvironments 120, a stand-alone cluster 130, a stand-alone server 140, anetwork 150, and a datacenter management server 160. Managed datacenter100 can also include one or more additional stand-alone clusters and oneor more stand-alone servers. Virtual machine environments 110 and 120,stand-alone cluster 130, and stand-alone server 140 are connected tonetwork 150 to provide an information processing capability that ismanaged by datacenter management server 160. A non-limiting example of anetwork 150 includes a Small Computer System Interface (SCSI) fabric, aFibre Channel (FC) fabric, an Internet SCSI (iSCSI) fabric, another datafabric or any combination thereof.

Virtual machine environment 110 includes a virtualization managementserver 112 that includes a virtual machine manager 114 (VMM) formanaging a virtualized cluster 116, and a virtualized server 118.Virtual machine environment 110 can also include one or more virtualizedclusters and one or more virtualized servers, and associated storageresources, as needed or desired. Virtual machine environment 110operates to provide the resources of the virtual machine environment toperform computing services for managed datacenter 100, such as webhosting, database processing, electronic mail and chat services, orother computing services, as needed or desired. VMM 114 launches andmaintains virtual machines on the processing resources of virtualizedcluster 116 and virtualized server 118, and each virtual machine isallocated to perform one or more of the computing services in the formof workloads that are executed on the virtual machines. VMM 114 caninclude a commercial virtual machine management suite, such asMicrosoft® System Center Virtual Machine Manager (SCVMM), VMware®vCenter™, Novell® ZENworks®, or another commercial virtual machinemanagement suite, as needed or desired. Virtualized cluster 116 andvirtualized server 118 include operating systems that are capable ofoperating in a virtualized environment, such as Microsoft® WindowsServer® 2008 (Win2k8), VMware® ESXi, Xen® Hypervisor, or anothervirtualization capable operating system, as needed or desired.

Virtual machine environment 120 includes a virtualization managementserver 122 similar to virtualization management server 112, and thatincludes VMM 124 similar to VMM 114, and that manages a virtualizedcluster 126, and a virtualized server 128. Virtual machine environment120 can also include one or more virtualized clusters and one or morevirtualized servers, and associated storage resources, as needed ordesired. Virtual machine environment 120 operates similarly to virtualmachine environment 110. Stand-alone cluster 130 and stand-alone server140 operate to perform computing services for managed datacenter 100 ina dedicated manner, providing functions such as one or more of adedicated web server, database server, electronic mail or chat server,or another type of server, as needed or desired. Stand-alone cluster 130and stand-alone server 140 can include operating systems that arecapable of operating in virtualized environment 110 or 120, or caninclude operating systems that preclude their operation in a virtualizedenvironment, as needed or desired

Datacenter management server 160 includes a datacenter infrastructuremanager 170, and a datacenter operations manager 180. Datacenterinfrastructure manager 170 includes an infrastructure viewer 172 and anasset deployment tool 174. Datacenter operations manager 180 provides across-platform management system for managed datacenter 100, includingdatacenter state, health, and tracking capabilities, resourceconfiguration and allocation capabilities, and alert and warningcapabilities. An example of datacenter operations manager 180 includesMicrosoft® System Center Operations Manager (SCOM), Intel® Data CenterManager, other datacenter management suites, or a combination thereof.

In a particular embodiment, datacenter operations manager 180 operatesto discover the resources of managed datacenter 100. As such, datacenteroperations manager 180 discovers virtualization management servers 112and 122, virtualized clusters 116 and 126, virtualized servers 118 and128, stand-alone cluster 130, and stand-alone server 140. Further,datacenter operations manager 180 determines that virtualized cluster116 and virtualized server 118 are associated with virtualizedenvironment 110 that is managed by virtualization management server 112and VMM 114, that virtualized cluster 126 and virtualized server 128 areassociated with virtualized environment 120 that is managed byvirtualization management server 122 and VMM 124, and that stand-alonecluster 130 and stand-alone server 140 are not associated withvirtualized environments 110 or 120.

Datacenter operations manager 180 also operates to inventory thediscovered resources of the managed datacenter. As such, datacenteroperations manager 180 inventories the hardware and software that areincluded in virtualization management servers 112 and 122, virtualizedclusters 116 and 126, virtualized servers 118 and 128, stand-alonecluster 130, and stand-alone server 140. Further, datacenter operationsmanager 180 inventories the operating systems that are included invirtualization management servers 112 and 122, virtualized clusters 116and 126, virtualized servers 118 and 128, stand-alone cluster 130, andstand-alone server 140. In particular, datacenter operations manager 180determines which commercial virtual machine management suite isoperating on virtualization management servers 112 and 122, and whichvirtualization capable operating system is operating on virtualizedclusters 116 and 126 and virtualized servers 118 and 128. Datacenteroperations manager 180 also determines whether or not stand-alonecluster 130 and stand-alone server 140 have virtualization capableoperating systems operating thereon, and if so which virtualizationcapable operating system is operating. In a particular embodiment, anoperating system operating on one or more of stand-alone cluster 130 andstand-alone server 140 can be a virtualization capable operating system,but can be in a state where the virtualization capability is disabled.In this case, datacenter operations manager 180 determines the state ofthe operating system of stand-alone cluster 130 and stand-alone server140.

Datacenter infrastructure manager 170 provides a cross-platformframework in which support personnel of managed datacenter 100 operateto identify virtualization capable resources of the managed datacenter,to determine the operating state of the virtualization capableresources, and if any of the virtualization capable resources are notdeployed within a virtualized environment, to deploy the virtualizationcapable resources to a virtualized environment. In particular,datacenter infrastructure manager 170 receives datacenter hierarchyinformation from datacenter operations manager 180. The datacenterhierarchy information includes the list of resources of manageddatacenter 100, the associations of the resources, and the inventory ofthe resources. The datacenter hierarchy information is used byinfrastructure viewer 172 to construct a hierarchical overview ofmanaged datacenter 100, as shown in FIG. 4 and described below.Infrastructure viewer 172 provides the hierarchical overview of manageddatacenter 100 to support personnel of the managed datacenter in theform of a user interface. The user interface permits the supportpersonnel to select virtualization capable resources, to select toenable the virtualization capabilities of the selected resources, toselect a virtualized environment, and to select to deploy the selectedresources to the selected virtualized environment. Asset deployment tool174 operates to receive the selections from the user interface, toenable the virtualization capabilities of the selected resources, and todeploy the selected resources to the selected virtualized environment.

FIGS. 2 and 3 illustrate a method of gathering datacenter hierarchyinformation of the resources of managed datacenter 100 to construct ahierarchical overview of the managed datacenter, to receive selectionsfrom the support personnel, and to enable the virtualizationcapabilities and to deploy the selected resources to the selectedvirtualized environment. Here, actions performed by elements of manageddatacenter 100 are represented in blocks 202 through 218. Block 202represents support personnel of the managed datacenter, block 204represents datacenter operations manager 180, block 206 representsdatacenter infrastructure manager 170, block 208 represents assetdeployment tool 174, block 210 represents infrastructure viewer 172,block 212 represents virtualization management servers 112 and 122,block 214 represents virtualized clusters 116 and 126 and virtualizedservers 118 and 128, block 216 represents stand-alone cluster 130, andblock 218 represents stand-alone server 140.

Support personnel 202 initiate a discovery process on datacenteroperations manager 204 in step 220. Datacenter operations manager 204issues requests for the identities of virtualization management servers212, virtualized cluster and servers 214, stand-alone cluster 216, andstand-alone server 218 in step 222. Virtualization management servers212, virtualized cluster and servers 214, stand-alone cluster 216, andstand-alone server 218 provide their identities to datacenter operationsmanager 204 in step 224. Virtualized cluster and servers 214 alsoprovide their associations to datacenter operations manager 204 in step224. Datacenter operations manager 204 issues requests for theinventories of virtualization management servers 212, virtualizedcluster and servers 214, stand-alone cluster 216, and stand-alone server218 in step 226. Virtualization management servers 212, virtualizedcluster and servers 214, stand-alone cluster 216, and stand-alone server218 provide their inventories to datacenter operations manager 204 instep 228. The inventories include the hardware, software, operatingsystems, commercial virtual machine management suites, andvirtualization capable operating systems and operating states.Datacenter operations manager 204 compiles the inventory into datacenterhierarchy information and provides the datacenter hierarchy informationto datacenter infrastructure manager 206 in step 230. Datacenterinfrastructure manager 206 provides the datacenter hierarchy informationto infrastructure viewer 210 in step 232. Infrastructure viewer 210constructs a hierarchical overview of managed datacenter 100.

FIG. 4 illustrates an example of a hierarchical overview 300 of manageddatacenter 100, including a depiction of infrastructure manager 310providing cross-platform management of a vCenter VMM environment 320, anSCVMM environment 340, and an unmanaged environment 370. vCenterenvironment 320 includes a cluster 330 having systems 332 and 334. SCVMMenvironment 340 includes a cluster 350 having systems 352 and 354, and aserver 360 having a system 362. Unmanaged environment 370 includes astand-alone cluster 380 having systems 382 and 384, and stand-aloneservers 390 including systems 392 and 394. Here, hierarchical overview300 indicates that systems 382, 384, and 392 are virtualization capableresources of managed datacenter 100, and that system 394 is not avirtualization capable resource.

Referring again to FIG. 3, infrastructure viewer 210 provideshierarchical overview 300 to support personnel 202 in step 234.Hierarchical overview 300 operates as a user interface, permittingsupport personnel 202 to make a selection of one or more availablevirtualization capable resource and to select to enable thevirtualization capabilities of the selected resources. The selectedvirtualization capable resources are communicated to datacenterinfrastructure manager 206 in step 236. Hierarchical overview 300 alsopermits support personnel 202 to make a selection of whichvirtualization environment the selected virtualization capable resourcesare to be deployed. The selected virtualization environments arecommunicated to datacenter infrastructure manager 206 in step 238.Datacenter infrastructure manager 206 launches asset deployment tool 208in step 240. Launching asset deployment tool 208 includes providing theasset deployment tool with the selected virtualization capableresources, the virtualization state of the selected resources, and theselected virtualization environment into which the selectedvirtualization capable resources are to be deployed. Asset deploymenttool 208 prepares the selected virtualization capable resource, that isthe selected one or more of stand-alone cluster 216 and stand-aloneserver 218, for deployment, and if necessary enables the virtualizationstate of the selected virtualization resource in step 242. Assetdeployment tool 208 directs the selected virtualization environment,that is the selected virtualization management server 212, to add theselected virtualization capable resource to the selected virtualizationenvironment in step 244. Asset deployment tool 208 provides the updateddatacenter hierarchy information to infrastructure viewer 210 in step246. Infrastructure viewer 210 provides an updated hierarchical overviewto support personnel 202 in step 248.

FIG. 5 illustrates an example of the updated hierarchical overview 305of managed datacenter 100. Here, cluster 380 and systems 382 and 384have been deployed to vCenter VMM environment 320, and system 392 hasbeen deployed to SCVMM environment 340. Because system 394 is not avirtualization capable resource, it is still depicted as part ofunmanaged environment 370.

FIG. 6 is a block diagram illustrating an embodiment of an informationhandling system 600, including a processor 610, a chipset 620, a memory630, a graphics interface 640, an input/output (I/O) interface 650, adisk controller 660, a network interface 670, and a disk emulator 680.In a particular embodiment, information handling system 600 is used tocarry out one or more of the methods described herein. In anotherembodiment, one or more of the systems described herein are implementedin the form of information handling system 600.

Chipset 620 is connected to and supports processor 610, allowing theprocessor to execute machine-executable code. In a particular embodiment(not illustrated), information handling system 600 includes one or moreadditional processors, and chipset 620 supports the multiple processors,allowing for simultaneous processing by each of the processors andpermitting the exchange of information among the processors and theother elements of the information handling system. Chipset 620 can beconnected to processor 610 via a unique channel, or via a bus thatshares information among the processor, the chipset, and other elementsof information handling system 600.

Memory 630 is connected to chipset 620. Memory 630 and chipset 620 canbe connected via a unique channel, or via a bus that shares informationamong the chipset, the memory, and other elements of informationhandling system 600. In another embodiment (not illustrated), processor610 is connected to memory 630 via a unique channel. In anotherembodiment (not illustrated), information handling system 600 includesseparate memory dedicated to each of the one or more additionalprocessors. A non-limiting example of memory 630 includes static randomaccess memory (SRAM), dynamic random access memory (DRAM), non-volatilerandom access memory (NVRAM), read only memory (ROM), flash memory,another type of memory, or any combination thereof.

Graphics interface 640 is connected to chipset 620. Graphics interface640 and chipset 620 can be connected via a unique channel, or via a busthat shares information among the chipset, the graphics interface, andother elements of information handling system 600. Graphics interface640 is connected to a video display 642. Other graphics interfaces (notillustrated) can also be used in addition to graphics interface 640 asneeded or desired. Video display 642 includes one or more types of videodisplays, such as a flat panel display, another type of display device,or any combination thereof.

I/O interface 650 is connected to chipset 620. I/O interface 650 andchipset 620 can be connected via a unique channel, or via a bus thatshares information among the chipset, the I/O interface, and otherelements of information handling system 600. Other I/O interfaces (notillustrated) can also be used in addition to I/O interface 650 as neededor desired. I/O interface 650 is connected via an I/O interface 652 toone or more add-on resources 654. Add-on resource 654 is connected to astorage system 690, and can also include another data storage system, agraphics interface, a network interface card (NIC), a sound/videoprocessing card, another suitable add-on resource or any combinationthereof. I/O interface 650 is also connected via I/O interface 652 toone or more platform fuses 656 and to a security resource 658. Platformfuses 656 function to set or modify the functionality of informationhandling system 600 in hardware. Security resource 658 provides a securecryptographic functionality and includes secure storage of cryptographickeys. A non-limiting example of security resource 658 includes a UnifiedSecurity Hub (USH), a Trusted Platform Module (TPM), a General PurposeEncryption (GPE) engine, another security resource, or a combinationthereof.

Disk controller 660 is connected to chipset 620. Disk controller 660 andchipset 620 can be connected via a unique channel, or via a bus thatshares information among the chipset, the disk controller, and otherelements of information handling system 600. Other disk controllers (notillustrated) can also be used in addition to disk controller 660 asneeded or desired. Disk controller 660 includes a disk interface 662.Disk controller 660 is connected to one or more disk drives via diskinterface 662. Such disk drives include a hard disk drive (HDD) 664, andan optical disk drive (ODD) 666, and can include one or more disk driveas needed or desired. ODD 666 can include a Read/Write Compact Disk(R/W-CD), a Read/Write Digital Video Disk (R/W-DVD), a Read/Write miniDigital Video Disk (R/W mini-DVD, another type of optical disk drive, orany combination thereof. Additionally, disk controller 660 is connectedto disk emulator 680. Disk emulator 680 permits a solid-state drive 684to be coupled to information handling system 600 via an externalinterface 682. External interface 682 can include industry standardbusses such as USB or IEEE 1394 (Firewire) or proprietary busses, or anycombination thereof. Alternatively, solid-state drive 684 can bedisposed within information handling system 600.

Network interface device 670 is connected to I/O interface 650. Networkinterface 670 and I/O interface 650 can be coupled via a unique channel,or via a bus that shares information among the I/O interface, thenetwork interface, and other elements of information handling system600. Other network interfaces (not illustrated) can also be used inaddition to network interface 670 as needed or desired. Networkinterface 670 can be a network interface card (NIC) disposed withininformation handling system 600, on a main circuit board such as abaseboard, a motherboard, or any combination thereof, integrated ontoanother component such as chipset 620, in another suitable location, orany combination thereof. Network interface 670 includes a networkchannel 672 that provide interfaces between information handling system600 and other devices (not illustrated) that are external to informationhandling system 600. Network interface 670 can also include additionalnetwork channels (not illustrated).

Information handling system 600 includes one or more applicationprograms 632, and Basic Input/Output System and Firmware (BIOS/FW) code634. BIOS/FW code 634 functions to initialize information handlingsystem 600 on power up, to launch an operating system, and to manageinput and output interactions between the operating system and the otherelements of information handling system 600. In a particular embodiment,application programs 632 and BIOS/FW code 634 reside in memory 630, andinclude machine-executable code that is executed by processor 610 toperform various functions of information handling system 600. In anotherembodiment (not illustrated), application programs and BIOS/FW codereside in another storage medium of information handling system 600. Forexample, application programs and BIOS/FW code can reside in HDD 664, ina ROM (not illustrated) associated with information handling system 600,in an option-ROM (not illustrated) associated with various devices ofinformation handling system 600, in storage system 690, in a storagesystem (not illustrated) associated with network channel 672, in anotherstorage medium of information handling system 600, or a combinationthereof. Application programs 632 and BIOS/FW code 634 can each beimplemented as single programs, or as separate programs carrying out thevarious features as described herein.

In the embodiments described herein, an information handling systemincludes any instrumentality or aggregate of instrumentalities operableto compute, classify, process, transmit, receive, retrieve, originate,switch, store, display, manifest, detect, record, reproduce, handle, oruse any form of information, intelligence, or data for business,scientific, control, entertainment, or other purposes. For example, aninformation handling system can be a personal computer, a consumerelectronic device, a network server or storage device, a switch router,wireless router, or other network communication device, a networkconnected device (cellular telephone, tablet device, etc.), or any othersuitable device, and can vary in size, shape, performance, price, andfunctionality. The information handling system can include memory(volatile (e.g. random-access memory, etc.), nonvolatile (read-onlymemory, flash memory etc.) or any combination thereof), one or moreprocessing resources, such as a central processing unit (CPU), agraphics processing unit (GPU), hardware or software control logic, orany combination thereof. Additional components of the informationhandling system can include one or more storage devices, one or morecommunications ports for communicating with external devices, as wellas, various input and output (I/O) devices, such as a keyboard, a mouse,a video/graphic display, or any combination thereof. The informationhandling system can also include one or more buses operable to transmitcommunications between the various hardware components. Portions of aninformation handling system may themselves be considered informationhandling systems.

When referred to as a “device,” a “module,” or the like, the embodimentsdescribed herein can be configured as hardware. For example, a portionof an information handling system device may be hardware such as, forexample, an integrated circuit (such as an Application SpecificIntegrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), astructured ASIC, or a device embedded on a larger chip), a card (such asa Peripheral Component Interface (PCI) card, a PCI-express card, aPersonal Computer Memory Card International Association (PCMCIA) card,or other such expansion card), or a system (such as a motherboard, asystem-on-a-chip (SoC), or a stand-alone device). The device or modulecan include software, including firmware embedded at a device, such as aPentium class or PowerPC™ brand processor, or other such device, orsoftware capable of operating a relevant environment of the informationhandling system. The device or module can also include a combination ofthe foregoing examples of hardware or software. Note that an informationhandling system can include an integrated circuit or a board-levelproduct having portions thereof that can also be any combination ofhardware and software.

Devices, modules, resources, or programs that are in communication withone another need not be in continuous communication with each other,unless expressly specified otherwise. In addition, devices, modules,resources, or programs that are in communication with one another cancommunicate directly or indirectly through one or more intermediaries.

Although only a few exemplary embodiments have been described in detailherein, those skilled in the art will readily appreciate that manymodifications are possible in the exemplary embodiments withoutmaterially departing from the novel teachings and advantages of theembodiments of the present disclosure. Accordingly, all suchmodifications are intended to be included within the scope of theembodiments of the present disclosure as defined in the followingclaims. In the claims, means-plus-function clauses are intended to coverthe structures described herein as performing the recited function andnot only structural equivalents, but also equivalent structures.

What is claimed is:
 1. A management server for a datacenter, themanagement server comprising: a memory device includingprocessor-executable code; and a processor configured to execute codeto: discover a first virtualized environment, a second virtualizedenvironment, and a virtualization capable system of the data center;discover a first resource of the first virtualized environment and asecond resource of the second virtualized environment; compile adatacenter hierarchy for the datacenter, the datacenter hierarchyincluding the first and second virtualized environments, the first andsecond resources, and the virtualization capable system; display ahierarchical overview of the datacenter hierarchy, the hierarchicaloverview including a first depiction of the first virtualizedenvironment and the first resource, a second depiction of the secondvirtualized environment and the second resource, and a third depictionof the virtualization capable system, the virtualization capable systembeing deployed as a stand-alone system of the datacenter, the first,second, and third depictions and the first and second resourceinformation being arranged according to a hierarchy of elements of thedata center; receive a first selection of one of the first and seconddepictions; receive a second selection of one of the first and secondresources; and deploy the virtualization capable system to the selectedvirtualized environment and to deploy the selected resource to theselected virtualized environment in response to receiving the first andsecond selections.
 2. The management server of claim 1, wherein indeploying the virtualization capable system to the virtualizedenvironment, the processor is further configured to execute code to: setthe virtualization capable system to a virtualization capable operatingstate; and receive updated datacenter hierarchy information in responseto setting the virtualization capable system to a virtualization capableoperating state.
 3. The management server of claim 2, wherein inresponse to receiving the updated datacenter hierarchy information, theprocessor is further configured to execute code to: display an updatedhierarchical overview of the datacenter, the updated hierarchicaloverview including a fourth depiction of the virtualization capablesystem as being deployed on the selected virtualized environment.
 4. Themanagement server of claim 1, wherein the datacenter hierarchyinformation further includes first inventory information for the firstvirtualized environment, and second inventory information for thevirtualization capable system.
 5. The management server of claim 4,wherein the second inventory information includes a virtualizationcapable operating state for the virtualization capable system.
 6. Themanagement server of claim 1, wherein compiling the datacenter hierarchyinformation is in response to receiving a request to discover the firstvirtualized environment and the virtualization capable system.
 7. Themanagement server of claim 1, wherein the virtualization capable systemincludes an operating system that is capable of operating in thevirtualized environment.
 8. The management server of claim 1, wherein,when the virtualization capable system is deployed as a stand-alonesystem of the datacenter, the virtualization capable system is operatingas at least one of a web server, database server, and electronic mailserver, and a chat server.
 9. A method of deploying virtualizationcapable assets in a datacenter, the method comprising: discovering afirst virtualized environment, a second virtualized environment, and avirtualization capable system of the data center; discovering a firstresource of the first virtualized environment and a second resource ofthe second virtualized environment; compiling a datacenter hierarchy forthe datacenter, the datacenter hierarchy including the first and secondvirtualized environments, the first and second resources, and thevirtualization capable system; determining, by a datacenter managementserver, hierarchy information for the datacenter based on the datacenterhierarchy, the hierarchy information including the first virtualizedenvironment of the datacenter, the first resource of the firstvirtualized environment, the second virtualized environment of thedatacenter, the second resource of the second virtualized environment,and the virtualization capable system of the datacenter, thevirtualization capable system being deployed as a stand-alone system ofthe datacenter, wherein the hierarchy information is arranged accordingto a hierarchy of elements of the datacenter; displaying a hierarchicaloverview of the datacenter, the hierarchical overview including a firstdepiction of the first virtualized environment including the firstresource, a second depiction of the second virtualized environmentincluding the second resource, and a third depiction of thevirtualization capable system, the hierarchical overview being based onthe hierarchy of elements of the datacenter; receiving a first selectionof one of the first and second depictions; receiving a second selectionof one of the first and second resources; and deploying thevirtualization capable system to the selected virtualized environmentand deploying the selected resource to the selected virtualizedenvironment in response to receiving the first and second selections.10. The method of claim 9, wherein in deploying the virtualizationcapable system to the virtualized environment, the method furthercomprises: setting the virtualization capable system to a virtualizationcapable operating state; and determining updated hierarchy information.11. The method of claim 10, wherein in response to determining theupdated hierarchy information, the method further comprises: displayingan updated hierarchical overview of the datacenter, the updatedhierarchical overview including a fourth depiction of the virtualizationcapable system as being deployed on the selected virtualizedenvironment.
 12. The method of claim 9, wherein the datacenter hierarchyinformation further includes first inventory information for the firstvirtualized environment and second inventory information for thevirtualization capable system.
 13. The method of claim 12, wherein thesecond inventory information includes a virtualization capable operatingstate for the virtualization capable system.
 14. The method of claim 9,wherein compiling the datacenter hierarchy information is in response toreceiving at the datacenter infrastructure manager a request to discoverthe first virtualized environment and the virtualization capable system.15. A non-transitory computer-readable medium having code for carryingout a method, the method comprising: discovering a first virtualizedenvironment, a second virtualized environment, and a virtualizationcapable system of the data center; discovering a first resource of thefirst virtualized environment and a second resource of the secondvirtualized environment; compiling a datacenter hierarchy for thedatacenter, the datacenter hierarchy including the first and secondvirtualized environments, the first and second resources, and thevirtualization capable system; determining, by a datacenter managementserver, hierarchy information for the datacenter based on the datacenterhierarchy, the hierarchy information including the first virtualizedenvironment of the datacenter, the first resource of the firstvirtualized environment, the second virtualized environment of thedatacenter, the second resource of the second virtualized environment,and the virtualization capable system of the datacenter, thevirtualization capable system being deployed as a stand-alone system ofthe datacenter, wherein the hierarchy information is arranged accordingto a hierarchy of elements of the datacenter; and displaying ahierarchical overview of the datacenter, the hierarchical overviewincluding a first depiction of the first virtualized environmentincluding the first resource, a second depiction of the secondvirtualized environment including the second resource, and a thirddepiction of the virtualization capable system, the hierarchicaloverview being based on the hierarchy of elements of the datacenter;receiving a first selection of one of the first and second depictions;receiving a second selection of one of the first and second resources;and deploying the virtualization capable system to the selectedvirtualized environment and deploying the selected resource to theselected virtualized environment in response to receiving the first andsecond selections.
 16. The computer-readable medium of claim 15, whereinin deploying the virtualization capable system to the virtualizedenvironment, the method further comprises: setting the virtualizationcapable system to a virtualization capable operating state; anddetermining updated hierarchy information.
 17. The computer-readablemedium of claim 16, wherein in response to determining the updatedhierarchy information, the method further comprises: displaying anupdated hierarchical overview of the datacenter, the updatedhierarchical overview including a fourth depiction of the virtualizationcapable system as being deployed on the selected virtualizedenvironment.
 18. The computer-readable medium of claim 15, wherein thedatacenter hierarchy information further includes first inventoryinformation for the first virtualized environment and second inventoryinformation for the virtualization capable system.
 19. Thecomputer-readable medium of claim 18, wherein the second inventoryinformation includes a virtualization capable operating state for thevirtualization capable system.
 20. The computer-readable medium of claim15, wherein compiling the datacenter hierarchy information is inresponse to receiving at the datacenter infrastructure manager a requestto discover the first virtualized environment and the virtualizationcapable system.